SUPPORT / SAMPLES & SAS NOTES
Problem Note 67395: A segmentation violation or read access violation occurs when you include the DEFER=YES option in a LIBNAME statement and use SAS® 9.4M7 (TS1M7)
 |  |  |  |  |
A read access violation or segmentation violation might occur after you access an SAP IQ library that has been defined using the DEFER=YES option.
In SAS® Enterprise Guide®, or SAS® Explorer, the error might occur while expanding the library. The session might stop responding, and then, depending on logging options, the workspace server log or SAS log shows a message similar to the following:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DOSSCHT ]
ERROR: Read Access Violation DOSSCHT
Exception occurred at (76528AD8)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFB76528AD8 000000B6D06CD6F0 sassiq:tkvercn1+0x7A98
00007FFB7658BB70 000000B6D06CD6F8 sasiosiq:tkvercn1+0xAB30
00007FFB766F7847 000000B6D06CD828 sasxdbi:tkvercn1+0x16807
00007FFB776F372E 000000B6D06CD878 sasyh:tkvercn1+0x126EE
00007FFB75DC9EBC 000000B6D06CDA48 sassqxb:tkvercn1+0x8E7C
00007FFB75DC37A5 000000B6D06CDB30 sassqxb:tkvercn1+0x2765
00007FFB75E9CCF6 000000B6D06CDB38 sassqx:tkvercn1+0x2BCB6
00007FFB75FAB5CD 000000B6D06CDB98 sasesql:tkvercn1+0xA58D
00007FFB75EAFA96 000000B6D06CDC50 sassqx:tkvercn1+0x3EA56
00007FFB75FAA607 000000B6D06CDCB0 sasesql:tkvercn1+0x95C7
00007FFB74E84FA7 000000B6D06CDCB8 sasyr:tkvercn1+0x33F67
00007FFB74E69358 000000B6D06CE0E0 sasyr:tkvercn1+0x18318
00007FFB74E6F780 000000B6D06CE1A0 sasyr:tkvercn1+0x1E740
00007FFB76EA70B0 000000B6D06CE1A8 sasdosm:tkvercn1+0x6070
00007FFB76EA489B 000000B6D06CF730 sasdosm:tkvercn1+0x385B
00007FFB73C3F5A8 000000B6D06CF738 sashost:Main+0x15268
00007FFB73C459CC 000000B6D06CFA60 sashost:Main+0x1B68C
00007FFB8FC113F2 000000B6D06CFA68 KERNEL32:BaseThreadInitThunk+0x22
00007FFB925A54F4 000000B6D06CFA98 ntdll:RtlUserThreadStart+0x34
ERROR: Generic critical error.
IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x8003c832
IOM LOGIC VOIMapWrcodeToWoiStatus() No wrcode mapping - using generic error (WOIRAISE): wrcode=0x8003c832
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DOSSCHT ]
ERROR: Read Access Violation DOSSCHT
Exception occurred at (76528AD8)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFB76528AD8 000000B6D06CD6F0 sassiq:tkvercn1+0x7A98
00007FFB7658BB70 000000B6D06CD6F8 sasiosiq:tkvercn1+0xAB30
00007FFB766F7847 000000B6D06CD828 sasxdbi:tkvercn1+0x16807
00007FFB776F372E 000000B6D06CD878 sasyh:tkvercn1+0x126EE
00007FFB75DC9EBC 000000B6D06CDA48 sassqxb:tkvercn1+0x8E7C
00007FFB75DC37A5 000000B6D06CDB30 sassqxb:tkvercn1+0x2765
00007FFB75E9CCF6 000000B6D06CDB38 sassqx:tkvercn1+0x2BCB6
00007FFB75FAB5CD 000000B6D06CDB98 sasesql:tkvercn1+0xA58D
00007FFB75EAFA96 000000B6D06CDC50 sassqx:tkvercn1+0x3EA56
00007FFB75FAA607 000000B6D06CDCB0 sasesql:tkvercn1+0x95C7
00007FFB74E84FA7 000000B6D06CDCB8 sasyr:tkvercn1+0x33F67
00007FFB74E69358 000000B6D06CE0E0 sasyr:tkvercn1+0x18318
00007FFB74E6F780 000000B6D06CE1A0 sasyr:tkvercn1+0x1E740
00007FFB76EA70B0 000000B6D06CE1A8 sasdosm:tkvercn1+0x6070
00007FFB76EA489B 000000B6D06CF730 sasdosm:tkvercn1+0x385B
00007FFB73C3F5A8 000000B6D06CF738 sashost:Main+0x15268
00007FFB73C459CC 000000B6D06CFA60 sashost:Main+0x1B68C
00007FFB8FC113F2 000000B6D06CFA68 KERNEL32:BaseThreadInitThunk+0x22
00007FFB925A54F4 000000B6D06CFA98 ntdll:RtlUserThreadStart+0x34
ERROR: Generic critical error.
IOM LOGIC VOIMapWrcodeToWoiStatus() Mapping error severity wrcode: 0x8003c832
IOM LOGIC VOIMapWrcodeToWoiStatus() No wrcode mapping - using generic error (WOIRAISE): wrcode=0x8003c832
With the DATASETS procedure, you might see a message that is similar to the following:
ERROR: An exception has been encountered.
Please contact technical support and provide them with the following traceback information:
Please contact technical support and provide them with the following traceback information:
The SAS task name is [DATASETS]
ERROR: Read Access Violation DATASETS
Exception occurred at (66EDDD09)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFD66EDDD09 000000A2732F46E0 sassiq:tkvercn1+0xCCB9
00007FFD670450FC 000000A2732F46E8 sasiosiq:tkvercn1+0x140AC
00007FFD66F4C196 000000A2732F48C8 sasxdbi:tkvercn1+0x2B146
00007FFD72AEAF55 000000A2732F4948 sasyh:tkvercn1+0x19F05
00007FFD669C9D17 000000A2732F4B58 sasqutil:tkvercn1+0x98CC7
00007FFD669BC6D5 000000A2732F7690 sasqutil:tkvercn1+0x8B685
00007FFD6693B919 000000A2732FF130 sasqutil:tkvercn1+0xA8C9
00007FFD66934646 000000A2732FF1B0 sasqutil:tkvercn1+0x35F6
00007FFD703D79C8 000000A2732FF1B8 sasxshel:tkvercn1+0x76978
00007FFD669DC22F 000000A2732FF450 sasqutil:tkvercn1+0xAB1DF
00007FFD66931CD9 000000A2732FF740 sasqutil:tkvercn1+0xC89
00007FFD6693121C 000000A2732FF7C0 sasqutil:tkvercn1+0x1CC
00007FFD69823B28 000000A2732FF7C8 sashost:Main+0x24F01
00007FFD6982D9FA 000000A2732FFBD0 sashost:Main+0x2EDD3
00007FFDE7EE7C24 000000A2732FFBD8 KERNEL32:BaseThreadInitThunk+0x14
00007FFDE834D4D1 000000A2732FFC08 ntdll:RtlUserThreadStart+0x21
ERROR: Read Access Violation DATASETS
Exception occurred at (66EDDD09)
Task Traceback
Address Frame (DBGHELP API Version 4.0 rev 5)
00007FFD66EDDD09 000000A2732F46E0 sassiq:tkvercn1+0xCCB9
00007FFD670450FC 000000A2732F46E8 sasiosiq:tkvercn1+0x140AC
00007FFD66F4C196 000000A2732F48C8 sasxdbi:tkvercn1+0x2B146
00007FFD72AEAF55 000000A2732F4948 sasyh:tkvercn1+0x19F05
00007FFD669C9D17 000000A2732F4B58 sasqutil:tkvercn1+0x98CC7
00007FFD669BC6D5 000000A2732F7690 sasqutil:tkvercn1+0x8B685
00007FFD6693B919 000000A2732FF130 sasqutil:tkvercn1+0xA8C9
00007FFD66934646 000000A2732FF1B0 sasqutil:tkvercn1+0x35F6
00007FFD703D79C8 000000A2732FF1B8 sasxshel:tkvercn1+0x76978
00007FFD669DC22F 000000A2732FF450 sasqutil:tkvercn1+0xAB1DF
00007FFD66931CD9 000000A2732FF740 sasqutil:tkvercn1+0xC89
00007FFD6693121C 000000A2732FF7C0 sasqutil:tkvercn1+0x1CC
00007FFD69823B28 000000A2732FF7C8 sashost:Main+0x24F01
00007FFD6982D9FA 000000A2732FFBD0 sashost:Main+0x2EDD3
00007FFDE7EE7C24 000000A2732FFBD8 KERNEL32:BaseThreadInitThunk+0x14
00007FFDE834D4D1 000000A2732FFC08 ntdll:RtlUserThreadStart+0x21
NOTE: The SAS System stopped processing this step because of errors.
The only workaround is to remove the DEFER=YES option from your LIBNAME statement or from the definition in the SAS metadata.
Click the Hot Fix tab in this note to access the hot fix for this issue.
Operating System and Release Information
| Product Family | Product | System | Product Release | SAS Release | ||
| Reported | Fixed* | Reported | Fixed* | |||
| SAS System | Base SAS | z/OS | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 |
| z/OS 64-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft® Windows® for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Enterprise 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Enterprise x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Pro 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8 Pro x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Enterprise 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Enterprise x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Pro 32-bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 8.1 Pro x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows 10 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2008 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 R2 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2008 for x64 | 9.4_M7 | 9.4 TS1M7 | ||||
| Microsoft Windows Server 2012 Datacenter | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 R2 Datacenter | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 R2 Std | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2012 Std | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2016 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Microsoft Windows Server 2019 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Enterprise 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Enterprise x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Home Premium 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Home Premium x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Professional 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Professional x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Ultimate 32 bit | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Windows 7 Ultimate x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| 64-bit Enabled AIX | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| 64-bit Enabled Solaris | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| HP-UX IPF | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Linux for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||
| Solaris for x64 | 9.4_M7 | 9.4_M8 | 9.4 TS1M7 | 9.4 TS1M8 | ||